Secure short-distance-based communication and enforcement system

ABSTRACT

A secure short-distance-based communication and enforcement system validates users in a validation and enforcement area and can check if users in the validation and enforcement area have been validated. Run-time IDs and keys that may be location-specific and device-specific may be generated and utilized for secure communication between mobile devices and zone computers and enforcement computers that execute validation and inspection.

BACKGROUND

For a variety of situations and reasons, it may be desirable to control.monitor and validate people's access to an area of interest. Forexample, it is not uncommon to include a gate to block entrance to aparking lot or secured facility. In another example, mass transitsystems, such as subways, often include some form of entrance control toenforce fare payment to ride the subway. Also, other places, likeconcert halls, stadiums, etc., still have conventional paper tickets,and people are employed to physically validate each individual ticket.

Controlling access to these areas can be automated. For example, a userhas a card key, and a reader is installed at a locked entrance. To gainaccess to the area, the user inserts his card key into the reader orplaces it in very close proximity to the reader so the reader can readthe card key. The information transmitted from the card key may be an IDand/or other information for the user and is processed throughappropriate business rules to determine if the user is authorized toaccess the area. If the user is determined to be authorized, the door isunlocked and the user is allowed to enter.

In other examples, instead of being automated, a person is responsiblefor monitoring or controlling an area. For example, a security guard isresponsible for checking people entering an area. In another example,passengers purchase tickets to ride on a train and after the passengersare on the train, a train conductor checks each person to determine ifthey have a ticket.

In the situations described above, either a user is required to have tocarry an additional card key and physically present the card key to thereader to gain access to the restricted area, which can be a majorinconvenience, or personnel, such as a security guard or a trainconductor, are needed to control or monitor an area, which is not alwayscost effective and is susceptible to human error. Furthermore, thesecurity of conventional systems is not optimal. In conventionalsystems, security codes used to validate the card keys are often storedon readers, and encoded into the card keys. They are highly susceptibleto hacking and as a result create a vulnerability of providingunauthorized access to restricted areas.

BRIEF DESCRIPTION OF DRAWINGS

Features of the present disclosure are illustrated by way of examplesshown in the following figures. In the following figures, like numeralsindicate like elements, in which:

FIG. 1 illustrates a secure short-distance-based communication andenforcement system, according to examples of the present disclosure;

FIGS. 2 and 3 show examples of zones in a validation area;

FIG. 4 shows a high-level flow chart of steps that may be performed forvalidation or enforcement by the a secure short-distance-basedcommunication and enforcement system, according to examples of thepresent disclosure;

FIGS. 5-6 shows additional details of the steps of FIG. 4, according toexamples of the present disclosure;

FIG. 7 shows additional details of the steps for validation checks,according to an example of the present disclosure;

FIG. 8 illustrates a block diagram of the a secure short-distance-basedcommunication and validation system, according to an example of thepresent disclosure;

FIGS. 9 and 10 illustrate flowcharts of methods performed for validationand enforcement, according to examples of the present disclosure;

FIG. 11 illustrates a method for enforcement, according to an example ofthe present disclosure; and

FIG. 12 illustrates a method for fare-based validation, according to anexample of the present disclosure.

DETAILED DESCRIPTION

For simplicity and illustrative purposes, the present disclosure isdescribed by referring mainly to examples thereof. In the followingdescription, numerous specific details are set forth in order to providea thorough understanding of the present disclosure. It will be readilyapparent however, that the present disclosure may be practiced withoutlimitation to these specific details. In other instances, some methodsand structures have not been described in detail so as not tounnecessarily obscure the present disclosure.

Throughout the present disclosure, the terms “a” and “an” are intendedto denote at least one of a particular element. As used herein, the term“includes” means includes but not limited to, the term “including” meansincluding but not limited to. The term “based on” means based at leastin part on.

A secure short-distance-based communication and enforcement systememploys low-powered beacons, zone computers and enforcement computers ina validation and enforcement area. Individuals communicate through theirmobile devices with the beacons and zone and enforcement computers tovalidate that the individuals are authorized to be in the validation andenforcement area and to provide on-the-spot verification thatindividuals are authorized to be in the validation and enforcement area.The system facilitates secure communication through short-distance-basedcommunication between the mobile devices and the zone and enforcementcomputers and through on-the-spot unique mobile device identifier (ID)and key generation. The unique mobile device ID and the key that enablethe secure communication are generated for a specific mobile device atits current location proximal to a zone computer. The unique mobiledevice ID may be determined from signals received from beacons for thecurrent location of the mobile device. For example, the unique mobiledevice ID is unique to the mobile device and a current location of themobile device when it transmits the mobile device ID to the zone and/orenforcement computer associated with the zone where the mobile device islocated.

By employing the short-distance-based, secure communication for messageexchange, the mobile device may remain in the user's pocket or bag andengage in activation and validation processes with the zone computer andother external computers to validate an individual. Additionally, thesystem may include multiple zones but the system employs techniques tominimize cross-talk between mobile devices and zone computers tofacilitate secure message exchange and validation of multiple userssimultaneously. The secure communication and cross talk minimization ofthe a secure short-distance-based communication and enforcement systemrepresent significant technical advantages over existing systems. Also,an application running on the mobile device that facilitates securityand other functions can easily be remotely updated over a network.However, card keys do not support this feature.

The system may be used in transit scenarios involving buses, trains,taxis, or other vehicles. For validation, the system may be provided forexample at the entrance and/or exit of the validation and enforcementarea, such as a the entrance to a train station. The entrance may begated, and validation is performed to open the gate or deny access tothe area by closing the gate. For example, an individual can use theirBluetooth-enabled mobile device to pay their fare at turnstiles, faregates, etc. They can have their fare deducted with the aid of theirmobile device while the mobile device remains inside their pockets orbag, or the fare can also be deducted by lightly tapping their mobiledevice on a zone computer. Also, the system may be used in non-gatedstations, or other non-gated environments where the individual does notpass through a gate or some other type of movable physical barrier toenter the validation and enforcement area. For example, the validationand enforcement area may be inside the vehicle or on a train stationplatform. The system determines whether the individual is in the areaand settled inside the area, such as settled inside the bus or settledon the train station platform, before conducting validation, which mayinclude fare payment. Similarly to the gated environment, the fare canbe deducted from the mobile device while the mobile device remainsinside a pockets or bag, or the fare can also be deducted by lightlytapping the mobile device on a zone computer, but the fare payment isdone inside the bus or train or other vehicle rather than at a faregate.

Also, regardless of whether validation is performed for example at agated entrance or inside the vehicle, an enforcement computer inside thevalidation and enforcement area, which may be inside the vehicle,performs on-the-spot verification to determine whether the individual isvalidated. The enforcement computer may be a mobile device that may becarried by an inspector or some other individual to verify that thepassengers are validated and have paid their fares. When an inspectordemands a proof of payment, the individual lightly taps their mobiledevice on the inspector's enforcement computer. Both the devicesinteract over Bluetooth or some other short-distance wirelesscommunication interface and the inspection result is displayed for theinspector on the enforcement computer. The enforcement computer can be amobile device carried by the inspector or a stationary computer that ismounted on a physical structure inside the validation and enforcementarea. The enforcement device or the user's mobile device may be awearable device, such as GOOGLE glass, a smart watch, etc., and may be acombination of a mobile device and a separate Bluetooth sensor that isconnected to the mobile device whereby communication is enabled via theBluetooth sensor. The validation and enforcement area may be a fare paidzone where an individual is required to pay a fare to be in the area. Aproof of payment can be demanded inside the validation and enforcementarea. By way of example, the validation and enforcement area can beinside a bus, train, subway, subway platform, train station, street carplatform, etc. Tickets for the fare can vary based on passenger profile(e.g., adult, child, student, senior, etc.), transit type (e.g., bus,subway, train, etc.), reusability (e.g., one time ticket, one day pass,weekly pass, etc.), time of travel (e.g., weekday, weekend, peak hours,off-peak hour, etc.).

FIG. 1 illustrates a secure short-distance-based communication andenforcement system 100, referred to as the system 100. The system 100 isemployed at validation and enforcement area 101. The validation andenforcement area 101 may be a geographic area or location and/or aphysical structure that individuals can enter and exit. The physicalstructure may be a mobile structure, such as a vehicle (e.g., bus,train, car, airplane, etc.), or a stationary structure such as abuilding or some other type of stationary structure. Also, thevalidation and enforcement area 101 may or may not have physicalstructures to control entry or exit into validation and enforcement area101. For example, a validation and enforcement area 101 may be an openarea.

The system 100 may be used for a non-gated environment, such as inside avehicle, train station platform, etc., or for a gated environment, suchas a subway entrance through a gate, or for any area where individualsmay enter or exit and validation and enforcement of validation can beperformed if the individual is detected in the validation andenforcement area 101. The system 100 may be used to execute fare paymentfor validation or to confirm that the ticket has been purchased and thefare has been paid for enforcement. Furthermore, the validation andenforcement area 101 may be divided into a plurality of sub-locations,also referred to as zones. Validation and enforcement may occur in anyof the zones in the validation and enforcement area 101. Multipleindividuals can be simultaneously validated by the system 100 in avalidation mode, and multiple individuals can be simultaneously checkedfor validation in an inspection mode for enforcement by the system 100.

Individuals in the validation and enforcement area 101 are checked, forexample, to determine whether they are approved to be in the validationand enforcement area 101 and/or to grant or deny approval of them beingin the validation area. For example, individuals in the validation andenforcement area 101 are supposed to be validated. For validation, theindividuals may have engaged in the validation process to be allowedentry into the validation and enforcement area 101 or may have engagedin the validation process after they entered the validation andenforcement area 101. Through an inspection process, the system 100 candetermine whether an individual in the validation and enforcement area101 has gone through validation and is approved to be in the validationand enforcement area 101. Accordingly, enforcement of validation mayinclude determining whether individuals in the validation andenforcement area 101 are approved to be in the validation andenforcement area 101.

Validation may be based on validation rules stored in the zone computersor a backend server or the mobile devices. In one example, validationmay include paying a fare associated with the validation and enforcementarea 101, such as paying a fare for riding a bus, train or taxi. Thevalidation rules may include rules to determine the amount of fare, suchas whether the fare is based on distance or number of stops or whether asingle fare is charged for any distance traveled, or based on other farepayment rules. Enforcement may include executing an inspection processto determine whether an individual has been approved to be in thevalidation and enforcement area 101. In one example, the enforcementincludes determining whether an individual paid the fare. “Users” and“individuals” are generally used interchangeably in the presentdisclosure and refer to anyone or anything that is to be validatedand/or inspected in the validation and enforcement area 101.

The system 100 may include end user mobile devices 130 that can each runa validation and enforcement application, shown as validation andenforcement applications 132 for the mobile devices 130, to receiveinformation from beacons 140 and exchange information with zonecomputers 150 to facilitate validation in the validation and enforcementarea 101. Mobile devices 130 a and 130 b are shown for users 131 a and131 b respectively but of course, any number of individuals using mobiledevices may be validated by the system 100. Also, multiple beacons 140,including beacons labeled 140 a-d, and multiple zone computers 150,including zone computers labeled 150 a-b, are shown, however, any numberof beacons and zone computers may be included in the system 100depending on various factors, such as how many users need to beprocessed simultaneously in the validation and enforcement area 101.

The beacons 140 are hardware that can broadcast beacon signals. Thebeacons 140 may be standalone devices or incorporated into anothersystem. A zone computer and/or an enforcement computer may have abeacon. The beacons 140 broadcast beacon signals at a short distance,such as up to 10 meters or a much shorter distance, such as up to 4centimeters. For example, the beacons 140 may be Bluetooth, BluetoothLow Energy (BLE), or near-field communication (NFC) beacons. The beacons140 may be part of a local positioning system, such as IBEACONS, thatare used to wirelessly determine the position of the mobile devices 130inside the restricted area 101. The beacons 140 may be positioned atstrategic locations inside the validation and enforcement area 101 tofacilitate accurate detection of a user within the validation andenforcement area 101. The broadcast range and power of the beacons canbe tuned per the environment. For example, the broadcast range of thebeacons is tuned to cover the boundaries of their respective zones. Forexample, the beacons 140 can broadcast towards the inside of theirrespective zone and may have a range to cover their zone but not muchfarther to prevent accidentally validating a mobile device that may beadjacent the validation and enforcement area 101 but not in it. Also,the validation and enforcement applications 132 running on the mobiledevices 130 can filter out the beacons below a specific power range oraccuracy or angle or azimuth or distance. Also, each of the zonecomputers 150 may be associated with a different zone in the validationand enforcement area 101, and a mobile device in a zone can identify thezone computer for the current zone based on location informationdetermined from signals received from the beacons in the zone. Thebeacons 140 broadcast a signal that invokes a validation process betweenthe mobile devices 130 and the zone computers 150. For example, afterreceiving signals from the beacons 140 a-d, the mobile device 130 acommunicates with the zone computer 150 a to validate the user 131 a,and similarly, the mobile device 130 b communicates with the zonecomputer 150 b to validate the user 131 a.

In one example, the beacons 140 and the zone computers 150 may beprovided at the entrance and/or exit of the validation and enforcementarea 101. For example, the beacons 140 and the zone computers 150 may beprovided at a gated entrance to control access to the validation andenforcement area 101. If a user is validated at the gate, the gate isopened to allow the user to enter. Validation at the gated environmentis further described with respect to FIG. 3.

As shown in FIG. 1, the system 100 also includes an enforcement computer175. Although a single enforcement computer 175 is shown, there may bemultiple enforcement computers in the validation and enforcement area101. The enforcement computer 175 may be a mobile device carried by aperson, shown as the enforcement person 177, checking the validation ofthe users 130. For example, the enforcement computer 175 is in closeproximity to the mobile device 130 a as shown in FIG. 1 and communicateswith the mobile device 130 a to check the validation of the user 131 a.Although the enforcement computer 175 is shown as a mobile device, theenforcement computer 175 may be a stationary computer mounted on aphysical structure, such as on a wall or another structure thatgenerally does not move within the validation and enforcement area 101.The enforcement computer 175 for example runs an inspection application172 to check the validation of the users 130.

The enforcement computer 175 may include an inspection beacon 176 thatbroadcasts an inspection signal through a short-distance communicationinterface in the enforcement computer 175. If the mobile devices 130receive the inspection signal, the validation and enforcementapplications 132 for the mobile devices 130 are placed in inspectionmode to disable validation, such as disabling buying fare products, anddisabling fare payment, through the validation and enforcementapplications 132 and to facilitate checking the validation of the users132. By disabling fare payment or other validation actions that can beperformed by the user, it prevents the user from being able to only paythe fare when they are being inspected or when they see an enforcementofficer inspecting passengers or are informed by other means of anenforcement officer inspecting passengers. Instead, the user has to paythe fare prior to entering inspection mode on the mobile device and thusencourages users to pay the fare righteously when entering thevalidation and enforcement area 101. Upon checking validation, if theuser is indicated as not being validated, the user may be removed fromthe validation and enforcement area 101, or charged an additionalpenalty fee in addition to the fare, or some other action may beperformed in response to determining the user has failed to validate.

In one example, instead of, or in addition to the enforcement computer175 including the inspection beacon 176, the enforcement computer 175can place the beacons 140, which may have previously been used forvalidation, into inspection mode. In the inspection mode, the beacons140 broadcast the inspection signal to facilitate the checking of thevalidation of the users 130. Assuming the beacons 140 can operate indifferent modes, when the beacons are not in inspection mode, thebeacons 140 operate in validation mode and broadcast a validation signalto facilitate validation. The inspection signal and the validationsignal may include a beacon ID. The beacon ID may identify the signal asan inspection signal or a validation signal. The signal may carryadditional information that can identify it as inspection signal or avalidation signal. For example, a unique ID in a beacon signal canidentify the beacon signal as an inspection signal or a validationsignal.

If the enforcement computer 175 is a stationary computer, it can inspectall the passengers that are in the validation and enforcement area 101,and may identify a particular seat or other location where the passengeris located based on triangulation and beacon information. Either themobile device or the enforcement computer may determine the location.The stationary enforcement computer 175 can update a backend server onenforcement status, and the enforcement officer can come on an as-needbasis.

The mobile devices 130 and the enforcement computer 175 (assuming it isa mobile device) may be any computer that a user may carry and that canrun an application. Examples of the computers may include mobile phones,tablets, wearable computers, such as GOOGLE glass or smart devicesembedded into clothing, a smart watch, fitness tracker, or wirelessenabled shoes, or some other type of mobile computer. The mobile devices130 and the enforcement computer 175 may include short-distance wirelesscommunication interfaces that can wirelessly communicate with beacons140 and zone computers 150 and the enforcement computer 175 when inproximity to the beacons 140 and the zone computers 150 and theenforcement computer 175. Also, in addition to receiving signals fromthe beacons 140, the mobile devices 130 and the enforcement computer 175themselves may operate as a beacon and broadcast a beacon signal or actas a peripheral, enabling services and/or characteristics, or act as acentral computer and start searching for peripherals with certainservices and/or characteristics and/or name and/or other uniqueidentifiers. The mobile devices 130 and the enforcement computer 175 mayinclude a beacon. In one example, a short-distance communicationinterface in a mobile device or the enforcement computer 175 canbroadcast a beacon signal to initiate communication.

In one example, the short-distance wireless communication interfaces mayinclude NFC interfaces. NFC is a set of standards for smartphones andother mobile devices to establish radio communication with each otherand other computers by touching them together or bringing them intoclose proximity. The close proximity may be a few inches or fewcentimeters (e.g., 4 centimeters). Other wireless interfaces may beused. For example, Bluetooth may be used and has a longer range, but mayconsume more battery power and is more susceptible to cross talk. Inanother example, BLE or Bluetooth 4.0 or future versions of Bluetoothwireless interfaces may be used. BLE is a wireless technology that isintended to provide reduced power consumption when compared to Bluetoothbut has a similar range to Bluetooth. The components of the system 100may have one or multiple types of short-distance wireless interfaces,which may have ranges from a few centimeters to a few meters. In anotherexample, the range is up to 100 feet. The zone computers 150, mobiledevices 130 and the enforcement computer 175 may include othercommunication interfaces as well, which are wired or wireless and may benetwork interfaces for communicating packets over a local area networkand/or a wide area network. However, communication between the beacons140/inspection beacon 176 and the mobile devices 130 and communicationbetween the zone computers 150 and the mobile devices 130 andcommunication between the enforcement computer 175 and the mobiledevices 130 may rely on short-distance wireless interfaces forcommunication with each other. Communication via a network interface maybe for exchanging messages with a backend server via a network, whichmay be done for validation and inspection.

The beacons 140 and beacon 176 may include small computers that may beattached to or embedded in a physical infrastructure. The beacons 140and beacon 176 may broadcast a message every x milliseconds (ms), wherex>1 ms and may be less than 200 ms but other intervals may be used andmay be based on the environment and use cases. The message may include aunique ID or a set of unique IDs or a combination of generic IDs andunique IDs. In one example, at least one part of the ID is generic andthe other part is unique. In one example, the ID may include auniversally unique identifier (UUID) a major ID and/or a minor ID. Forexample, one of the identifiers is generic (e.g., UUID and/or the majorID) and may be the same for all beacons that belong to or are for aparticular entity, such as for the same company or the same mass transitsystem, or may vary between different entities or restriction levelwithin the same company or mass transit system. The other unique ID(e.g., minor ID) may help identify a particular location orsub-location. For example, the major ID may be the same for all beaconsthat belong to a particular location within the system, such as aspecific rail station or a bus stop or train, and the minor ID may bedifferent for each subway car or can be unique to the beacon and can beassociated with a particular sub-location within a location. Also, themajor ID or the minor ID may identify the beacon as an inspection beaconor a beacon for validation.

The mobile devices 130 listen for the broadcasts from the beacons 140,which may contain the unique identifiers for each beacon, or inputs fromwhich the unique identifiers may be calculated or computed or derived orlooked up in an internal data store. When a mobile device is in range ofone or more of the beacons 140, unique identifiers received from thebeacons at the mobile device may invoke a detection mode in the mobiledevice to determine whether the mobile device is in proximity to atleast one of the zone computers 150 or the enforcement computer 175 inthe validation and enforcement area 101. This is referred to asdetection or detection mode. In detection mode, to determine whether themobile device is in proximity to a zone computer or the enforcementcomputer 175, the unique beacon identifiers, signal strength (such asreceived signal strength indicator (RSSI), transmission power, and/orreceived Power) of the beacon's broadcasts, broadcast zone, broadcastaccuracy, azimuth and/or angle of the beacon signal (e.g., calculatedfrom the received wireless broadcast) are used to identify the locationof the mobile device. If the mobile device detects that it is in thevalidation and enforcement area 101, it may engage in communication withthe zone computer or the enforcement computer 175 for validation orenforcement. This may involve the mobile device getting into aperipheral mode, wherein the mobile device may start sending messagebroadcasts over the wireless interface (e.g. Bluetooth 4.0), like abeacon. For example, the mobile device acts as a Bluetooth peripheraland advertises, broadcasts, transmits, and/or enables its servicesand/or characteristics using one or more of unique mobile IDs. The zonecomputer or the enforcement computer 175 may use the unique mobiledevice ID to identify the mobile device or the services/characteristicsadvertised, broadcasted, transmitted, and/or supported by the mobiledevice or the fare payment application on the mobile device. In anotherexample, the zone computer or the enforcement computer 175 broadcasts amessage indicating that it is available for validation or enforcementand the mobile device ID which is calculated by the computer is includedin the message. The mobile device receives the message, determineswhether the mobile device ID in the message matches the mobile device IDcalculated by the mobile device, and if it does match, initiating amessage exchange for authentication and validation.

The zone computers 150 include computers that may be provided in thevalidation and enforcement area 101 for authentication and validation ofusers in the validation and enforcement area 101. A zone computer maysupport an entire validation area or a zone in the validation area. Thezone computers 150 engage in message exchange and validation processeswith the mobile devices 130 for authentication and validation after themobile devices enter peripheral mode, which may be invoked after themobile devices 130 detect that they are in the validation andenforcement area 101 and that the mobile devices 130 are settled. Forexample, a process is executed to establish a secure communicationchannel between a mobile device and a zone computer through run-time keygeneration, which may be based on the ID of beacons and otherinformation. Messages may be exchanged via the secure communicationchannel to perform validation. In one example, validation may includefare-based validation, such as when payment of a fare is required.

Similarly, the enforcement computer 175 engages in secure messageexchange and processes with the mobile devices 130 for authenticationand to check validation, which is further described below. Both the zonecomputers 150 and the enforcement computer 175 may be connected to aback-end server via the Internet or another wide area network to provideupdates and perform other functions which may include validation-relatedfunctions.

FIGS. 2 and 3 show examples of validation in the validation andenforcement area 101. FIG. 2 shows an example of validation performed ina non-gated environment, such as validation performed after the users130 enter the validation and enforcement area 101. This may includecharging a fare after the users 130 enters a bus or after the users 130enter a subway car. FIG. 3 shows an example of validation performed in agated environment, such as validation performed at an entrance of asubway station. Regardless of whether the validation and enforcementarea 101 is a gated environment or a non-gated environment, when theusers 130 are inside the validation and enforcement area 101, theenforcement computer 175 may be used to check the validation of theusers 130 such as shown in FIG. 1 and further described below.

FIG. 2 shows an example of a configuration of beacon placement inmultiple zones 1-3 in the validation and enforcement area 101. Thevalidation and enforcement area 101 may be inside a vehicle, such as asubway car. The subway car may have multiple zones 1-3, which may beadjacent doors to get in and out of the subway car. In this example,user 131 a is in zone 1, and user 131 b is outside zone 2 and outsidethe subway car (i.e., outside validation and enforcement area 101). Whenthe user 131 a enters zone 1, the mobile device 130 a for the user 131 areceives the signals from beacons 140 a-d. The validation andenforcement application 132 a running on the mobile device 130 a entersdetection mode and detects that it is in a zone in the validation andenforcement area 101 and is in proximity to the zone computer 150 a. Forexample, the validation and enforcement application 132 a uses thebeacon information from signals received from the beacons 140 a-d todetermine its location and calculate the passenger's position in zone 1.The beacon signals relative strength, angle, azimuth, etc. and thelocation information derived from the major ID or minor ID or carried inthe payload of the signals are used to determine the precise location ofthe user 131 a. The precise location may indicate that the mobile device130 a or the user 131 a is in zone 1 and may further identify an areawithin zone 1, such as a seat.

At the current location of user 131 b, the mobile device 130 b of user131 b receives beacon signals from beacons 140 b and 140 e-g. The beaconsignals relative strength, angle, azimuth, etc. and the locationinformation derived from the major ID or minor ID or carried in thepayload of the signals from beacons 140 b and 140 e-g are used todetermine the precise location of the user 131 b. Based on thisinformation, the validation and enforcement application 132 b maydetermine that the user 131 b is outside the validation and enforcementarea 101 and not enter peripheral mode. For example, the validation andenforcement application 132 b may determine that the signals are frombeacons assigned to different zone computers, such as zone computers 150a-c. Also, from the signal strength, angle, and azimuth, the validationand enforcement application 132 b may determine that the signals frombeacons 140 b and 140 g have a signal strength below a threshold, and anangle and azimuth that are indicative of beacons associated withdifferent zones and different zone computers. Thus, the validation andenforcement application 132 b may ascertain that the closest beacons arebeacons 140 e-f. The validation and enforcement application 132 b mayfurther determine that since it is not receiving signals, or receivingsignals that are too weak, from at least three or all four beacons forthe same zone, that it is outside the validation and enforcement area101. Therefore, the validation and enforcement application 132 b doesnot enter peripheral mode and does not engage in validation.

Also, the zone computers 150 may be connected to displays (not shown) toprovide indication to the user of whether they are validated or not. Forexample, zone computer 150 a may display a message indicating user 131 ais validated. If multiple users are in the zone, a user ID may bedisplayed along with an indication of whether the user is validated. Forexample, a check mark indicates a person is validated. If the person isnot validated, the display may show an X, and may provide additionalinformation, such as “See Attendant” or “Insufficient Funds” if theuser's account does not have sufficient funds to pay a fare. Also,external systems may be invoked, such as to alert attendants or toautomatically replenish funds in a user's account or change user'saccess privileges.

FIG. 3 shows an example of validation that may be performed for a gatedvalidation and enforcement area 101. The lanes 110 may be zones of anentry point. The beacons 140 and/or the zone computers 150 may beembedded in the physical structures of the lanes 110. The zone computers150 may electronically control movable physical barriers 160, such asgates, turnstiles, etc. Each electronically-controlled movable physicalbarrier may be located in a different zone. For example, movablephysical barriers 160 a-b in lanes 110 a-b allow or deny access to thevalidation and enforcement area 101. Also, the zone computers 150 may beconnected to displays 151, such as displays 151 a-b, to provideindication to the users 131 of whether they are approved to enter thevalidation and enforcement area 101 or not. Other information may alsobe displayed. For example, an arrow indicates a lane is open. The checkmark shown on the display 151 b indicates a user is validated and thegate opens. If the person is not validated, the display may show an X,such as shown on display 151 a, and may provide additional information,such as “See Attendant” or “Insufficient Funds” if the user's accountdoes not have sufficient funds to pay a fare. Also, external systems maybe invoked, such as to alert attendants or to automatically replenishfunds in a user's account.

FIG. 4 shows a high-level flow chart of steps performed by the system100, and FIG. 5 shows additional details of the steps and theinteraction between the various sub-systems of the system 100, includingthe mobile devices 130, beacons 140, and zone computers 150 that performthe steps, according to an embodiment. Referring to FIG. 4, steps areshown for detection at step 10, activation at step 11, exchange at step12 and validation at step 13.

At step 10, for detection, a mobile device determines whether it is inproximity to a zone computer (e.g., determining whether the mobiledevice is a validation area of a zone computer) based on informationreceived from beacons. Determining proximity to a zone computer mayinclude determining whether the mobile device is within a predetermineddistance to a beacon or a plurality of beacons associated with a zonecomputer. Determining the distance to a beacon may be estimated based onsignal strength, signal angle and azimuth, etc. According to an example,mobile device 130 a shown in FIG. 1 receives signals from the beacons140 a-d. Each signal includes a beacon ID, e.g., a UUID, major ID and/ora minor ID. Each beacon ID may be determined so that it can be used toidentify its location, such as station, zone, etc. The beacons 140 a-dmay also transmit a small payload containing the location information orany other information that can help to calculate the locationinformation.

In one example, triangulation-based detection is performed to determinewhether the mobile device 130 a is in a zone. For example, thevalidation and enforcement application 132 a running on the mobiledevice 130 a registers for beacon notifications with a specific uniqueID or IDs or part of the IDs, e.g. UUID and/or major ID and/or minor IDor a list of UUIDs, major IDs and/or minor IDs. For example, the UUIDsor the major IDs may be the same for all beacons provided by the sameentity, such as all beacons for the same mass transit company or allbeacons for the same train station. So, for example, the UUIDsbroadcasted by the beacons 140 may be the same because they are for thesame entity or same train station. The validation and enforcementapplication 132 a stores a list of UUIDs, major IDs and minor IDs thatit may respond to. The mobile device 130 a listens for broadcastedunique IDs from beacons. If the unique IDs of the beacon signals thatare received are registered, such as stored in the list, the validationand enforcement application 132 a determines whether it is in a zone inthe validation and enforcement area 101. For example, in response torecognizing broadcasts from beacons 140 a-d or at least one of thebeacons, using beacon signal attributes such as distance and azimuth,the validation and enforcement application 132 a in mobile device 130 adetermines that it is within a predetermined distance (e.g., within 1meter) to at least 1 of the beacons 140 a-d. Thus, the validation andenforcement application 132 a determines that it is in a zone, such aszone 1, and then proceeds to activation at step 111.

In another example, tap-based detection is performed. For example, theuser lightly taps the mobile device 130 a on or near beacon 140 a or atzone computer 150 a if it also acts as a beacon. The range of the beaconmay be tuned so that the mobile device 130 a needs to be in closeproximity to detect the beacon, such as within 3-4 centimeters, or themobile device might take into consideration the signal strength, zone,accuracy and other factors of the beacon broadcast to determine theproximity with the beacons, and decide accordingly. If a beacon uniqueID or IDs are received that are registered at the mobile device 130 a,in response to the tapping or placement in close proximity to thebeacon, the application 132 a performs activation at step 11. In anotherexample, an intent of the user to enter validation is determined forexample based on measurable user actions performed on the mobile device,such as shaking the mobile device twice, audible command spoken into themobile device, etc.

At step 11 shown in FIG. 4, after detecting proximity to a zone computerat step 10, activation is performed. For example, activation may includedetermining whether the mobile device 130 a of the user 131 a is in azone in the validation and enforcement area 101. FIG. 2 shows an examplewhere the mobile device 130 a is detected in zone 1. Activation may alsoinclude determining whether the mobile device 130 a is in a settledstate for a non-gated area, such as shown in FIG. 2. For the gatedenvironment, such as shown in FIG. 3, a settled state need not bedetermined for activation. The settled state may be a mobile device thatis determined to be stationary in the validation and enforcement area101 for a predetermined period of time, and may be determined for thenon-gated enforcement and validation area to prevent improper farecharging such as when a user quickly moves in and out of the enforcementand validation area 101 as is described below.

If the mobile device 130 a is determined to be in a zone in thevalidation and enforcement area 101 and in the settled state for anon-gated area, a run-time unique mobile device ID and encryption keysare calculated for the mobile device 130 a for future secure messageexchange with the zone computer 150 a, and a peripheral mode isactivated. The peripheral mode is entered to communicate with the zonecomputer associated with the current location of the mobile device 132a, which is zone computer 150 a for zone 1 in FIG. 2.

Determining whether the mobile device 130 a is in a settled state may beperformed to prevent accidentally entering into validation for farepayment. For example, the settled state indicates whether a mobiledevice is in a predetermined location for a predetermined amount oftime. For example, if a user enters a bus with a validation andenforcement area and then exits the bus immediately without riding thebus, the mobile device of the user may receive a signal from a beacon inthe bus. However, because the user does not settle in the bus,validation is not performed and the user is not charged.

The settled state may be determined from motion sensors and based ontime. Measurements from different sensors inside the mobile device 130 a(e.g., accelerometer, gyroscope, and/or motion co-processor) may be usedto determine whether the mobile device 130 a is stationary or is moving,and whether the mobile device 130 a is moving in a direction outside thezone or outside the validation area and a rate of the movement. Also,the motion of the vehicle is determined in order to determine whetherthe mobile device is stationary or in motion while the vehicle is mobileor while the vehicle is stationary. If the mobile device 130 a is movingwhile the vehicle is in motion, then the mobile device 130 a may stillbe considered to be in a settled state but other factors may beconsidered. Also, the length of time the mobile device 130 a isstationary may be ascertained from the sensor measurements to determinewhether it is in a settled state. In one example, the validation andenforcement application 132 a activates the peripheral mode if themobile device 130 a is determined to be in a settled state, or thevehicle is in motion for a predetermined period of time, and/or themobile device 130 a has been inside the vehicle for a certain amount oftime.

Unique ID determination for the mobile device may vary depending on howdetection was performed. For example, if triangulation-based detectionwas performed, the unique IDs (like major ID, minor ID and optionalpayload) from the beacons used for triangulation may be used tocalculate the unique ID or IDs for the mobile device. If tap-baseddetection was performed, the unique ID or IDs may be calculated usingthe unique ID or IDs from the beacon that was tapped (e.g. major ID,minor ID and optional payload from the beacon that was tapped). Theperipheral mode is enabled in the mobile device to communicate with thezone computer for the lane using the unique IDs for the services and/orcharacteristics. Examples of unique ID calculation functions aredescribed below.

In one example, the unique ID or IDs for the mobile device arecalculated using the information received from the beacons and/or zonecomputer as the input. Thus, the unique ID is specific to the currentlocation of the mobile device. The unique ID is not valid (or may not bevalid) at a different location The current location may be a particularzone in the validation area 101 or a specific seat in the zone.

A unique ID calculation function may be used to calculate the unique IDor IDs for the mobile device from the information received from one ormore beacons. An example of a unique ID calculation function isdescribed below. Assume the following: Row=Minor ID/1000; Sequence=MinorID %1000, whereby % represents the modulo operator; Location=MajorID/1000; and Sub-Location=Major ID %1000.

If triangulation-based detection was used at step 10, the followingsteps may be performed to calculate the unique ID or IDs for the mobiledevice. The detected beacons are sorted based on the signal strength(like RSSI, transmission power, received power, etc.) in descendingorder. Beacons may be filtered, e.g., removed from the list, if theirreceived signal strength indicator does not fall within a predeterminedvalue, or if they proximity is unknown or if the azimuth and angledoesn't meet predetermined requirements or a combination of these. Forexample, if the signal strength is too weak, such as determined bycomparing the signal strength to a predetermined threshold, thecorresponding beacon may be removed from the list. Then, the top “x”beacons from the list are identified where x>1. In one example, x isgreater than or equal to 3. If a plurality of beacons from the top “x”beacons have the required signal strength, then, the major ID and minorID are used to calculate the Row, Sequence, Location and Sub-locationinformation from the beacon signals, which is in turn is used togenerate the unique ID or IDs. Beacons in the same lane may have thesame location, sub location and row value.

If tap-based detection was used at step 10, then the following isperformed with all the beacons that are found in range. At step 1, thebeacons are sorted based on signal strength, accuracy, etc. indescending order and the first beacon in the list is identified or theyare sorted in ascending order and the last beacon in the list isidentified. Checks on the azimuth, angle, distance, accuracy areperformed to ensure the mobile device is in the desired proximity of thebeacon. At step 2, the signal strength value for this beacon should begreater than or equal to a predetermined value, e.g., <=−30 dB. At step3, the row, location and sub-location information of the beacon is usedto generate the unique ID or IDs.

One example of a unique ID calculation function for either tap-baseddetection or triangulation-based detection is: Unique ID=[Pre-definedUnique ID Part]+[Location]+[Sub location]+[Row]. In other examples,mathematical functions, such as a conventional hash function, RSA, etc.,are employed that use these three values along with other values, toderive the unique ID or IDs. In other examples, mathematical functionscan be used to determine these three values, which in turn become inputto other mathematical functions to derive the unique ID or IDs. Theinput values may include current time, location, sub-location, row,sequence, etc.

At step 12 shown in FIG. 4, for message exchange, the mobile device andthe zone computer for the zone exchange information for validation.Regardless of the way detection and activation were performed, messageexchange occurs in the same way. The zone computer determines whetherthe mobile device is within its area of validation if the mobile deviceis within range. The area of validation may be a zone. For example, thearea of validation for zone computer 150 a is zone 1 shown in FIG. 2. Todetermine whether the mobile device is within the zone computer's areaof validation, the zone computer may use the distance, signal strength,the azimuth and angle of the mobile device relative to the zone computeror a plurality of these values to determine the mobile device'slocation. The zone computer initiates a connection with the validationand enforcement application on the mobile device if the mobile device isin the area of validation and the mobile device is broadcasting oradvertising or transmitting one or more unique IDs and/or haspredetermined services and/or characteristics. Then message exchange mayoccur for validation. For example, the zone computer 150 a and thevalidation and enforcement application 132 a on the mobile device 130 amay enter into authentication to establish the identity of both sides.After authentication, data is exchanged between the zone computer 150 aand the validation and enforcement application 132 a for validation. Thezone computer 150 a and the validation and enforcement application 132 amay request additional data resulting in multiple exchanges. In anotherexample, the mobile device may initiate the connection with the zonecomputer and then engage in authentication and then validation.Authentication in either case may include determination of keys forsecure communication.

At step 13 shown in FIG. 4, validation is performed. Validation may beperformed the same way regardless of how detection was performed. Forexample, the zone computer makes a decision on whether the user isvalidated based on data exchanged with the mobile device, equipmentoperational data, and/or real-time services hosted on a backend. Theequipment operational data may include fare rules (different fare types,concession types, fare validity window, etc.), transfer rules, locationinformation (e.g., zone computer location), etc. The real-time servicesmay include fare payment. In another example, the backend may storeauthorization information for individuals to determine whether the useris cleared to be in the validation area 101. The decision of whether theuser is validated is communicated to the user, such as through a displayconnected to the zone computer or through the mobile device. Forexample, the zone computer may send information to the validation andenforcement application related to the validation decision and/or theuser's account (e.g., new balance, transaction summary, etc.). Thevalidation and enforcement application may communicate the decision tothe user using inbuilt features like haptic feedback, audionotification, visual notification, etc., based on user's preferences.

FIG. 5 shows details of the steps of FIG. 4 and illustrates theinteraction between the devices in the system 100 performing the steps.For example, assume user 131 a is entering zone 1 and has mobile device130 a running validation application 132 a, such as shown in FIGS. 1 and2. The mobile device 130 a interacts with beacons 140 a-d and zonecomputer 150 a when performing the steps.

The beacons 140 a-d periodically broadcast their unique IDs and optionalpayload indicating location. At step A, the mobile device 130 a receivesthe broadcasts when in range. At step B, assuming the validation andenforcement application 132 a is not already running, the validation andenforcement application 132 a is launched for example if the operatingsystem of the mobile device 130 a recognizes the beacon IDs asregistered beacon IDs. For example, beacon IDs that have a predeterminedUUID, major ID and/or minor ID invoke launching of the validation andenforcement application 132 a. If tap-based detection is used, thevalidation and enforcement application 132 a may be launched if the usertaps on or near a beacon and the unique ID of the beacon is registered.At step C, the validation and enforcement application 132 a entersdetection mode to determine whether it is in a zone, such as zone 1 andwhether the mobile device is in a settled state. Detection may includetap-based detection or triangulation-based detection. After detectingthe mobile device 130 a is in zone 1 and in a settled state, thevalidation and enforcement application 132 a enters activation mode tocalculate the unique ID of the mobile device 130 based on informationderived from the signals of the beacons 140 a-d. The validation andenforcement application 132 a enters peripheral mode and a message withthe unique ID of the mobile device is broadcasted or sent to a localzone computer, e.g., zone computer 150 a, at step E. The broadcast maybe a short range broadcast, such as using BLE or Bluetooth.

At step F, the zone computer 150 a receives the message with the mobiledevice unique ID from the mobile device 130 a assuming it is withinrange, and determines whether the mobile device 130 a is within the areaof validation of the zone computer 150 a. An example of the area ofvalidation may be a zone, such as zone 1. The zone computer 150 a usesthe distance, signal strength and optionally the azimuth and angle ofthe mobile device 130 a, which may be determined from the receivedmessage, to determine whether the mobile device 130 a is in its area ofvalidation. For example, in addition to receiving the message from themobile device 130 a, the zone computer 150 a may receive a message froma mobile device in zone 2. However, the zone computer 150 a determinesthat only the mobile device 130 a is currently in its area ofvalidation, i.e., zone 1. Accordingly, the zone computer 150 acommunicates with the mobile device 130 a for validation but not themobile device in zone 2 at this instant.

At step G, if the mobile device 130 a is determined to be in zone 1, thezone computer 150 a initiates communication with the mobile device 130a. For example, the zone computer 150 a sends an acknowledgment messageto the mobile device 130 a that includes the mobile device unique ID sothe mobile device 130 a knows that the zone computer 150 a is ready toproceed to validation. In another example, the zone computer 150 a maybroadcast or transmit an acknowledgment message that is encrypted withthe mobile device unique ID to the mobile device 130 a. Only the mobiledevice 130 a can decrypt the acknowledgment message sent from the zonecomputer 150 a because no other mobile device knows the key. In yetanother example, the zone computer 150 a and the mobile device 130 acalculate the mobile device unique ID independently using the sameinputs and the same function. For example, the inputs for the unique IDcalculation function described above may be determined by the mobiledevice 130 a and broadcasted or sent to the zone computer 150 a with themobile device unique ID. Both the zone computer 150 a and the mobiledevice 130 a store the same function for calculating the mobile deviceunique ID. The zone computer 150 a also calculates the mobile deviceunique ID. The zone computer 150 a determines if the received mobiledevice ID matches the calculated mobile device ID to determine whetherto continue with the process, e.g., initiate communication,authentication and validation.

Mutual authentication is performed at step H. The mobile device 130 aand the zone computer 150 a may exchange messages for authentication toestablish identities of both sides. The mutual authentication mightresult in a generation of a key or set of keys that are then used forfurther encryption, decryption, enciphering, deciphering, etc. Aconventional key encryption algorithm may be used.

At step I, the zone computer 150 a determines whether the mobile device130 a or its user 131 a is validated. Validation may include exchangingmessages with a backend server not shown and/or the mobile device 130 ato get the information needed to perform validation. In one example,validation may include a fare payment determination and the zonecomputer 150 a may determine whether the fare can be paid from a useraccount for the user 131 a. At step J, validation results are returnedto the mobile device 130 a. The zone computer 150 a may also sendinformation to the related to the user's account (e.g., new balance,transaction summary, etc.). At step K, if the user 131 a is validated,e.g., a fare is paid, the validation and enforcement application 132 acan mute itself from the beacons in the same fare paid zone to preventfrom being double-charged for the duration of the fare validity. If thevalidation is denied, the zone computer 150 a can display an indicationon a display that validation failed. If the user 131 a is validated, thezone computer 150 a can display an indication that the user 131 a isvalidated.

After steps E and F are performed, keys may be used for securecommunication. As described above, keys may be used to encrypt messagesbetween the mobile device 130 a and the zone computer 150 a.Accordingly, the key may be used for secure communication between themobile device 130 a and the zone computer 150 a. Also, the mobile deviceunique ID and/or the key are run-time. For example, they may begenerated in real-time for the validation process and are only valid forthe current time and location and for the particular mobile device. Thisprovides additional security by improving the robustness of the key. Inanother example, MACing might be used to secure the communicationbetween the mobile device 130 a and the zone computer 150 a. In anotherexample, both encryption and MACing might be used to secure thecommunication between the mobile device 130 a and the zone computer 150a.

At step I, validation may vary depending on whether information forvalidation is stored locally or stored in a backend server. For example,for a “stored value” system, information for validation is storedlocally on the mobile device in a secure manner. For example,information, such as user profile, balance amount, passes and concessioninformation are stored securely on the mobile device. In a “credential”systems, the information is stored on a backend server (e.g., thecloud), and the mobile device only stores credentials, such as useraccount number, and the information is retrieved from the backend serverin real time for completing validation or enforcement of transactions.

FIG. 6 shows details of the steps of FIG. 4 for a gated validation andenforcement area, such as shown in FIG. 3. For example, in FIG. 3,assume user 131 a is entering lane 110 a and has mobile device 130 arunning validation and enforcement application 132 a, such as shown inFIGS. 1 and 2. The mobile device 130 a interacts with beacons 140 a-dand zone computer 150 a when performing the steps.

The beacons 140 a-d periodically broadcast their unique IDs and optionalpayload indicating location. At step A, the mobile device 130 a receivesthe broadcasts when in range. At step B, if the validation andenforcement application 132 a isn't already running, the validation andenforcement application 132 a is launched for example if the operatingsystem of the mobile device 130 a recognizes the unique IDs of thebeacons as registered unique IDs. For example, beacon IDs that have apredetermined UUID and/or major ID and/or minor ID invoke launching ofthe validation and enforcement application 132 a. If tap based detectionis used for the beacons, the validation and enforcement application 132a may be launched if the user taps on or near a beacon and the uniqueIDs of the beacon is registered. At step C, the validation andenforcement application 132 a enters detection mode to determine whetherit is in a lane, such as lane 110 a. Detection may include tap-baseddetection or triangulation-based detection. After detecting the mobiledevice 130 a is in lane 110 a, the validation and enforcementapplication 132 a enters activation mode to calculate the unique ID orIDs based on information from the beacons and a message with the uniqueID or IDs may be broadcasted or sent to a local zone computer, e.g.,zone computer 150 a, at step E. For example, a mobile device unique ID,which includes the calculated unique ID or IDs, is broadcasted by themobile device 130 a. The broadcast may be a short range broadcast, suchas using BLE, Bluetooth 4.0.

At step F, the zone computer 150 a receives the broadcasted message withthe mobile device unique ID from the mobile device 130 a assuming it iswithin range, the zone computer 150 a validates that the broadcastedmessage contains the unique ID or IDs related to the sub-location anddetermines whether the mobile device 130 a is within the area ofvalidation of the zone computer 150 a. An example of the area ofvalidation is shown in FIG. 3, such as the lane 110 a. The zone computer150 a uses the distance, signal strength and optionally the azimuth andangle of the mobile device 130 a, which may be determined from thereceived message, to determine whether the mobile device 130 a is in itsarea of validation. For example, in addition to receiving the messagefrom the mobile device 130 a, the zone computer 150 a may receive amessage from a mobile device around the lane 110 b. However, the zonecomputer 150 a determines that only the mobile device 130 a is currentlyin its area of validation, i.e., lane 110 a or has the correct unique IDor IDs. Accordingly, the zone computer 150 a will only communicate withthe mobile device 130 a for validation at this instant.

At step G, if the mobile device 130 a is determined to be in lane 110 a,the zone computer 150 a initiates communication with the mobile device130 a using the unique ID or IDs as a reference. For example, the zonecomputer 150 a sends an acknowledgment message to the mobile device 130a that includes the mobile device unique ID so the mobile device 130 aknows that the zone computer is ready to proceed to validation. Inanother example, the zone computer 150 a may broadcast or transmit anacknowledgment message that is encrypted with a key to the mobile device130 a. Only the mobile device 130 a can decrypt the acknowledgmentmessage sent from the zone computer 150 a because no other mobile deviceknows the key. In yet another example, the zone computer 150 a and themobile device 130 a calculate the mobile device unique ID independentlyusing the same inputs and the same function. For example, the inputs forthe unique ID calculation function described above may be determined bythe mobile device 130 a and broadcasted or sent to the zone computer 150a with the mobile device unique ID. Both the zone computer 150 a and themobile device 130 a store the same function for calculating the mobiledevice unique ID. The zone computer 150 a also calculates the mobiledevice unique ID. The zone computer 150 a determines if the receivedmobile device ID matches the calculated mobile device ID to determinewhether to continue with the process, e.g., initiate communication,authentication and validation.

Mutual authentication is performed at step H. The mobile device 130 aand the zone computer 150 a may exchange messages for authentication toestablish identities of both sides. The mutual authentication mightresult in a generation of a key or set of keys that are then used forfurther encryption, decryption, enciphering, deciphering, etc. Aconventional key encryption algorithm may be used.

At step I, the zone computer 150 a determines whether the mobile device130 a or its user 131 a is validated. Validation may include exchangingmessages with a backend server not shown and/or the mobile device 130 ato get the information needed to perform validation. In one example,validation may include a fare payment determination and the zonecomputer 150 a may determine whether the fare can be paid from a useraccount for the user 131 a. At step J, validation results are returnedto the mobile device 130 a. At step K, the zone computer 150 a sends asignal to open gate 160 a for the lane 110 a if the user 131 a isvalidated. The signal may be an internal signal if the gate 160 a ispart of the system 100 or it may be transmitted to an external system ifthe gate 160 a is part of an external system. If the validation isdenied, the zone computer 150 a can display an indication on the display151 a that access to the restricted area is denied. If the user 131 a isvalidated, the zone computer 150 a can display an indication on thedisplay 151 a that the they are approved to access (or exit) therestricted area.

After steps E and F are performed, keys may be used for securecommunication. As described above, the keys may be used to encrypt orencipher the messages between the mobile device 130 a and the zonecomputer 150 a. Accordingly, the key may be used for securecommunication between the mobile device 130 a and the zone computer 150a. Also, the mobile device unique ID and/or the key are run-time. Forexample, they may be generated in real-time for the validation processand are only valid for the current time and location and for theparticular mobile device. This provides additional security by improvingthe robustness of the key. In another example, MACing might be used tosecure the communication between the mobile device 130 a and the zonecomputer 150 a. In another example, both encryption and MACing might beused to secure the communication between the mobile device 130 a and thezone computer 150 a.

FIG. 7 shows detailed steps for enforcement. The steps shown in FIG. 4for validation are also applicable for enforcement. Referring to FIG. 4,steps are shown for detection at step 10, activation at step 11,exchange at step 12 and validation at step 13. For enforcement, atdetection step 10, the mobile devices 130 determine whether they are inproximity to the enforcement computer 175 based on an inspection signalreceived from the inspection beacon 176 shown in FIG. 1. A unique mobiledevice ID is calculated for each mobile device at activation step 11based on the inspection signal. At exchange step 12, messages areexchanged between the mobile devices 130 and the enforcement computer175 using the mobile device ID and via short distance communicationinterfaces to determine whether the mobile devices have been validated,e.g., whether fares have been paid. The enforcement computer 175 maycommunicate with a backend server to determine whether a user iscurrently validated. For example, the backend server may store a list ofusers that have paid the fare and when they paid fare and detailsdescribing what the fare payment was for. At step 13, a determination ismade as to whether the user was previously validated and an indicationof whether the user was validated is displayed on the enforcementcomputer 175, and a message may be sent from the enforcement computer175 to the mobile device with the indication. FIG. 7 shows details ofthese steps 10-13.

The steps of FIG. 7 are described with respect to FIG. 1 and show theinteraction between the mobile device 130 a, the inspection beacon 176,and the enforcement computer 175. At step A, the inspection beacon 176broadcasts an inspection signal. The inspection signal for exampleincludes a UUID, a major ID and/or a minor ID, such as described abovewith respect to the signals broadcasted from the beacons 140. Aninspection beacon for example announces that the enforcement individual176 (e.g., an inspection officer that checks if fares have been paid) isin the vicinity by broadcasting the inspection signal. The inspectionsignal is distinguished from signals broadcasted from the beacons 140for example based on information in the UUID, major ID and/or minor IDthat identifies the signal as an inspection signal to the mobile devices130.

In one example, the enforcement computer 175 may be a mobile device thatincludes the inspection beacon 176. In another example, the enforcementcomputer 175 sends a signal to the beacons 140 to place them ininspection mode, and the beacons 140 broadcast the inspection signals.

At step B, the validation and enforcement application 132 a on themobile device 130 a detects the inspection signal and disables anyfeatures for buying fare products or making fare payment at step C. Thisprevents the “mischievous” user from only paying the fare if they arebeing inspected or if they sense they will be inspected. For example,the validation and enforcement application 132 a allows the user 131 ato create and login to an account for fare payment which may be storedand managed by a backend system (not shown). The user may enable anddisable auto payment, pay a fare on demand, link a credit card or bankaccount to the account, etc. The fare payment feature of the validationand enforcement application 132 a is disabled so a user cannot buy fareproducts or pay a fare through the validation and enforcementapplication 132 a when the inspection signal is received by the mobiledevice 130 a and detected by the validation and enforcement application132 a. When, the inspection signal is received, the validation andenforcement application 132 a operates in inspection mode and disablesfare payment features and fare products buying features. The inspectionsignal may include a UUID or a major ID that are registered to invokelaunching the validation and enforcement application 132 a if it is notalready running. The validation and enforcement application 132 a mayalready be running because validation may have recently occurred. Also,the inspection signal is recognized by the validation and enforcementapplication 132 a as an inspection signal for example based on a code inthe major ID or in the minor ID.

In one example, the inspection signal broadcasted from the inspectionbeacon 176 is a Bluetooth or BLE signal. In another example, tap-baseddetection is performed and the inspection signal may be a Bluetooth orBLE signal tuned for a shorter distance, such as 3-4 centimeters. Fortap-based detection, the user 131 a may tap the mobile device 130 a onthe enforcement computer 175 carried by the enforcement person 177 toreceive the inspection signal. The inspection signal in both examplesincludes the UUID, major ID and/or the minor ID and may include otherinformation, such as signal strength, location information, etc.

At step D, the validation and enforcement application 132 a calculates aunique inspection ID based on information derived from the inspectionsignal. The validation and enforcement application 132 a entersperipheral mode and a message with the inspection ID is broadcasted orsent to the enforcement computer 175 at step E. The broadcast may be ashort range broadcast, such as using BLE, Bluetooth, or NFC.

Similar to the unique mobile device ID derived for validation, such asdescribed with respect to step D in FIGS. 5 and 6, the inspection ID maybe calculated using the major ID, minor ID and optional payload from theinspection signal. Location information may be used to calculate theinspection ID. Location information may be derived from information inthe UUID or the payload of the inspection signal if it is provided.Location information may be determined by the mobile device 130 a forexample from internal location sensors, such as GPS, or fromtriangulation determined from signals received from local beacons, suchas the beacons 140 a-d. Thus, the inspection ID may be unique to themobile device 130 a at its current location. Examples of ID calculationfunctions are described above.

At step F, the enforcement computer 175 receives the inspection ID fromthe mobile device 130 a assuming it is within range, and determineswhether the mobile device 130 a is within an area of inspection of theenforcement computer 175. An example of an area of inspection may be anarea within a one meter radius of the current location of theenforcement computer 175. The area of inspection may be smaller iftap-based detection was used at step B, such as 5-10 centimeter radius.The enforcement computer 175 may use the distance, signal strength andoptionally the azimuth and angle of the broadcasted signal from themobile device 130 a to determine the location of the mobile device 130 aand whether it is in the area of inspection.

At step G, if the mobile device 130 a is determined to be in the area ofinspection, the enforcement computer 175 initiates communication withthe mobile device 130 a using the inspection ID. For example, theenforcement computer 175 sends an acknowledgment message to the mobiledevice 130 a that includes the inspection ID so the validation andenforcement application 132 a in the mobile device 130 a knows that theenforcement computer 175 is ready to proceed to checking the validationof the user 131 a. In another example, the enforcement computer 175 maybroadcast or transmit an acknowledgment message that is encrypted with akey to the mobile device 130 a. Only the mobile device 130 a can decryptthe acknowledgment message sent from the enforcement computer 175because no other mobile device knows the key. In yet another example,the enforcement computer 175 and the mobile device 130 a calculate theinspection ID independently using the same inputs and the same function.For example, the inputs for the inspection ID calculation functiondescribed above may be determined by the mobile device 130 a andbroadcasted or sent to the enforcement computer 175 along with theinspection ID calculated by the mobile device 130 a. Both theenforcement computer 175 and the mobile device 130 a store the samefunction for calculating the unique inspection ID. The enforcementcomputer 175 also calculates the inspection ID. The enforcement computer175 determines if the received inspection device ID that is calculatedmatches the received inspection ID to determine whether to continue withthe process, e.g., initiate communication, authentication and validationdetermination.

Mutual authentication is performed at step H. The mobile device 130 aand the enforcement computer 175 may exchange messages forauthentication to establish identities of both sides. The mutualauthentication may include generation of a key or set of keys that arethen used for further encryption, decryption, enciphering, deciphering,etc. A conventional key encryption algorithm may be used.

At step I, the enforcement computer 175 and the mobile device 130 aexchange messages to determine whether the user 131 a was validated.Validation checking may include exchanging messages with a backendserver not shown and/or the mobile device 130 a to get the informationneeded to check validation. In one example, checking validation mayinclude a determination of whether a fare was paid. Messages exchangedfor validation checking are referred to as inspection messages.

For example, the validation and enforcement application 132 a on themobile device 130 a may receive a transaction summary from a back endserver if a fare was paid. The enforcement computer 175 may request thetransaction summary from the validation and enforcement application 132a, and receive it in response to the request. The enforcement computer175 may determine from the details of the transaction summary whetherthe fare was paid for the current area or ride. For example, thetransaction summary may include time of the transaction, location wheretransaction occurred, and type of ticket that was purchased. From thedetails of the transaction summary, the enforcement computer 175determines whether the fare was paid. For example, if the fare was for asingle ride ticket valid for the current day to any destination, thenthe enforcement computer 175 determines the user 131 a was validated. Inanother example, the validation and enforcement application 132 a sendsa message that automatic payment is enabled, and the fare will bededucted from the user account when the destination is reached.

The enforcement computer 175 may get transaction information from abackend server to check validation. For example, the validation andenforcement application 132 a may send an ID for the user account of theuser 131 a to the enforcement computer 175. Using the account ID, theenforcement computer 175 may request fare payment information or anindication of whether the user 131 a paid the fare from the backendserver that stores user account information.

At step J, the results of the validation check are displayed for exampleon the enforcement computer 175 so the enforcement person 177 can viewthe results and take appropriate action if needed. Appropriate action ifthe fare was not paid may include having the user 131 a make payment,pay a penalty fee, issue a ticket indicating notice of failed validationto the user, and/or remove the user 131 a from the validation andenforcement area 101. If the results indicate that the fare was paid,the enforcement computer 175 may mark the ticket as consumed andinspected if it is a single ride ticket, and send information of themarked ticket to the backend server.

At step K, the results of the validation check are sent to the mobiledevice 130 a, and the validation and enforcement application 132 a maydisplay or notify the user 131 a of the results of the validation checkthrough another type of input/output device at step L. After the resultsof the validation check are received or an acknowledgement is receivedfrom the enforcement computer 175 or the backend server that avalidation check has been performed, the validation and enforcementapplication 132 a may exit the inspection mode, thus enabling the farepurchase feature of the validation and enforcement application 132 a.The user 131 a may pay the fare if the validation check indicates thefare was not paid.

After steps E and F are performed, encryption keys may be used forsecure communication. As described above, the encryption keys may beused to encrypt messages between the mobile device 130 a and theenforcement computer 175 or the inspection ID may be included in themessages and the information in the messages is only accepted if itincludes the correct inspection ID. Accordingly, the inspection IDand/or encryption keys may be used for secure communication between themobile device 130 a and the enforcement computer 175. Also, theinspection ID and/or the encryption keys may be run-time, i.e.,generated in real-time and are only valid for the current time andlocation and mobile device. This provides additional security.

FIG. 8 shows block diagrams of the mobile device 130 a, the zonecomputer 150 a, and the enforcement computer 175 of the system 100 butis representative of any of the mobile devices, zone computers andenforcement computers that may be used in the system 100. Also, some ofthe components of the mobile device 130 a, the zone computer 150 a, andthe enforcement computer 175 are shown, and it will be apparent to oneof ordinary skill in the art that the devices and computers may includeother components not shown.

The mobile device 130 a may include multiple interfaces 601, wired orwireless, for communicating with other devices. For example, interface601 a may be a Wi-Fi interface or a cellular interface or may includeboth interfaces. The interface 601 a for example is a network interfacethat can communicate with a backend server via a network. 601 b mayinclude a Bluetooth interface. In one example, message exchanges betweenthe mobile device 130 a and the zone computer 150 a are done throughBluetooth and the interface 601 b but other interfaces may be used, suchas BLE, Bluetooth 4.0 or other future versions of Bluetooth or NFC.Similarly, message exchanges between the mobile device 130 a and theenforcement computer 175 are done through Bluetooth and the interface601 b but other short-distance interfaces may be used, such as Bluetooth4.0 or other future versions of Bluetooth or NFC. Interface 601 c may bea NFC interface, but the mobile device 130 a may have both Bluetooth andNFC interfaces and multiple other interfaces. Interface 601 b may be forcommunicating with the beacons 140, for example, for triangulation-basedor tap-based detection.

The mobile device 130 a includes a processor 602 and data storage 604.The processor 602 for example is an integrated circuit. The processor602 may be a chipset with central processing unit and/or customprocessing circuits, such as an application-specific integrated circuit(ASIC) or field-programmable gate array (FPGA). The processor 602 mayrun an operating system (OS) 603 and applications, including validationand enforcement application 132 a, for the mobile device 130 a. The OS603 and the applications are stored in data storage 604. Any informationused by the validation and enforcement application 132 a and the OS 603may be stored in the data storage 604. For example, the data storage 604may store registered UUIDs for determining whether to launch thevalidation and enforcement application 132 a in response to receiving abeacon signal with a registered UUID. The data storage 604 may storetransaction summaries for purchased fare tickets that can be used forchecking validation. Also, the data storage 604 may store keys, locationinformation, movement information determined from motion sensors 620,etc. The data storage 604 may include memory and/or non-volatile datastorage.

The mobile device 130 a includes input/output (I/O) devices 610, such askeyboard, touch screen display, speaker, etc. The I/O devices 610 mayprovide audio, visual and/or tactile output to indicate whether a userhas been validated or results of a validation check. The mobile device130 a also includes motion sensors 620. Examples of motion sensors 620may include accelerometer, gyroscope, and/or a motion co-processor.Information from the motion sensors 620 may indicate information ormeasurements of the motion of the mobile device 130 a. This informationmay be used to determine whether the mobile device 130 a is in a settledstate.

The zone computer 150 a includes a processor 612 and a data storage 613.The processor 612 is an integrated circuit. The processor may executesoftware or firmware or comprise custom processing circuits, such as anapplication-specific integrated circuit (ASIC) or field-programmablegate array (FPGA). The data storage 613 may include memory and/ornon-volatile data storage. The data storage 613 may store software orfirmware including machine readable instructions and may store anyinformation used by the zone computer 150 a. The software or firmwaremay include subroutines or an application for detection 620,authentication 621 and validation 622, such as described with respect toFIGS. 4-6. The zone computer 150 a may include I/O devices or beconnected to an I/O device, such as a display, to provide indication tothe user of whether they are validated.

The zone computer 150 a also includes multiple interfaces 620, wired orwireless, for communicating with other devices. For example, interface620 a may be a Wi-Fi interface or a cellular interface or may includeboth interfaces. 620 b may include a Bluetooth or Bluetooth 4.0 or BLEinterface. In one example, message exchanges between the mobile device130 a and the zone computer 150 a are done through a Bluetooth but otherinterfaces may be used. 620 c may be a NFC interface, but the mobiledevice 130 a may have both BLE and NFC interfaces. The interfaces 620 band 620 c are short-distance communication interfaces. A short-distancecommunication interface may have a communication range of few meters(e.g., Bluetooth or BLE) or centimeters (e.g., NFC). The range isgenerally much shorter than Wi-Fi or cellular. The short-distancecommunication interface may cover a sub-location or a sub-location andits adjacent sub-location. The zone computer 150 a may connect via anetwork interface of interfaces 620 to a server backend via the Internetor another wide area network or a local area network for validation,which may include fare payment.

If the zone computer 150 a is used in a gated environment, such as shownin FIG. 3, it may include an actuator driver circuit 170 to controlactuation of the physical barrier for the sub-location of the zonecomputer. In response to determining the user is validated, the zonecomputer 150 a sends a signal to the actuator driver circuit 170 toinvoke opening of the physical barrier, such as gate 160 a for lane 110a. For example, the processor 612 validates a user associated with themobile device 130 a and sends a signal to the actuator driver circuit170. The actuator driver circuit 170 drives an actuator of the gate 160a to open the gate 160 a shown in FIG. 3. The processor 612 may alsodrive the circuit 170 to close the gate 160 a. In one example, theglobal positioning system (GPS) sensor on the mobile device may be usedto determine when the user enters and exits the mass transit system inorder to determine the fare amount and open the gate 160 a if the fareis paid when the user is exiting.

The enforcement computer 175 includes a processor 632 and a data storage633. The enforcement computer 175 may be a mobile device or a stationarycomputer. The processor 632 is an integrated circuit. The processor mayexecute software or firmware or comprise custom processing circuits,such as an application-specific integrated circuit (ASIC) orfield-programmable gate array (FPGA). The data storage 633 may includememory and/or non-volatile data storage. The data storage 633 may storesoftware or firmware including machine readable instructions and maystore any information used by the enforcement computer 175. The softwareor firmware may include the inspection application 172 that performs thefunctions described above with respect to FIG. 7.

The enforcement computer 175 also includes multiple interfaces 630,wired or wireless, for communicating with other devices. For example,interface 630 a may be a Wi-Fi interface or a cellular interface or mayinclude both interfaces. The interface 630 a for example is a networkinterface that can communicate with a backend server via a network. 630b may include a Bluetooth interface and 630 c may be a BLE or NFCinterface or some other type of short-distance interface, but theenforcement computer 175 may have both BLE and NFC interfaces.

The enforcement computer 175 may include the inspection beacon 176 thatbroadcasts the inspection signal or the inspection beacon 176 may be aseparate device from the enforcement computer 175. The beacons 140 arealso shown. As stand-alone devices, the beacons 140 and/or theinspection beacon 176 may include circuits that may be programmed with aUUID and an interface for broadcasting their signals. In one example,the inspection beacon 176 and the beacons 140 may broadcast theirsignals using Bluetooth. If the beacons 140 and/or the inspection beacon176 are incorporated in the zone computer 150 a or the enforcementcomputer 175, they may use the interface of the computer for theirbroadcasts. Also, exchange of messages between the mobile device 130 a,the zone computer 150 a and the enforcement computer 175 may be throughBluetooth.

FIG. 9 shows a flowchart of a method 900 that may be performed by amobile device, such as the mobile device 130 a in the system 100, forchecking validation. The method 900 is described by way of example withrespect to the system 100 shown in FIG. 1 but may be performed in othersystems. At 901, the mobile device 130 a receives a signal from a beaconvia its short-distance communication interface, such as via BLE or NFC.For example, the inspection beacon 176 broadcasts an inspection signaland it is received by the mobile device 130 a.

At 902, the mobile device 130 a determines whether the received beaconsignal is from a registered beacon. For example, the OS 603 running onthe mobile device 130 a determines whether the UUID or major ID in thereceived beacon signal is from a registered UUID or major ID. If thereceived beacon signal is from a registered beacon, the information forthe beacon signal is sent to the validation and enforcement application132 a. If the validation and enforcement application 132 a is notrunning, the OS 603 launches the validation and enforcement application132 a and sends the inspection signal information to the validation andenforcement application 132 a. The mobile device 130 a stores theregistered beacon IDs (e.g., the major IDs) for the beacons 140 and theinspection beacon 176 so the OS 603 recognizes their beacon signals. At904, if the beacon signal is not recognized it is ignored.

At 903, the validation and enforcement application 132 a determineswhether the received beacon signal is a validation signal or aninspection signal. A code in the beacon signal may identify it as avalidation signal or an inspection signal. The validation signal is abeacon signal sent by one or more of the beacons 140, and may be used toinvoke validation, such as described in FIGS. 4-6. If the beacon signalis a validation signal, at 905, validation is performed such asdescribed with respect to FIGS. 4-6. For example, a unique mobile deviceID is calculated based on information in the beacon signal and is usedto deduct the fare.

If the beacon signal is an inspection signal, such as from theinspection beacon 176, then a validation check is performed, such asdescribed with respect to FIG. 7. For example, at 906, fare purchase isdisabled. For example, the validation and enforcement application 132 amay include a fare payment feature that allows the user 131 a to pay afare by logging into their account. This feature is disabled. Also, thebuying of fare products is disabled so the user cannot enable paymentthrough another means during inspection.

At 907, an inspection ID is calculated based on information receivedfrom the inspection signal. The inspection ID may be unique to themobile device 130 a and the current location of the mobile device 130 awhen the inspection ID is calculated. At 908, messages are exchangedwith the enforcement computer 175 using the inspection ID and one ormore encryption keys via a short-distance communication interface (e.g.,Bluetooth) to authenticate the mobile device 130 a and to determinewhether the user 131 a was validated. As discussed with respect to FIG.7, this may include determining whether the user 131 a paid the fare.Results of the validation check are determined at 909. The enforcementcomputer 175 may determine the results of the validation check anddisplay them on the enforcement computer 175 and send the results to themobile device 130 a.

At 910, after the validation results are received by the validation andenforcement application 132 a, the fare payment is enabled. If the user131 a was determined to not have paid the fare, the user 131 a may nowpay the fare through the validation and enforcement application 132 a.

FIG. 10 shows a flowchart of a method 1000 that may be performed by anenforcement computer, such as the enforcement computer 175, in thesystem 100. At 1001, the enforcement computer 175 determines whether aninspection ID is received from the mobile device 130 a via ashort-distance communication interface of the enforcement computer 175.If the inspection ID is received, the enforcement computer 175determines whether the mobile device 130 a is in an area of inspectionfor the enforcement computer 175 at 1002. If tap-based detection wasused, the enforcement computer 175 can determine whether the user tappedor came within close proximity (e.g., within 4-5 cm) of the enforcementcomputer 175. Alternatively, the enforcement computer 175 may scan forall Bluetooth mobile devices in range looking for devices which exposecertain services/characteristics, and determines a mobile device is inthe area of inspection based on signal strength, dwell angle, etc.

At 1003, if the mobile device 130 a is not in the area of inspection,the inspection ID is ignored. If the mobile device 130 a is in the areaof inspection, the enforcement computer 175 determines whether the user131 a associated with the mobile device 130 a was validated at 1004. At1004, the validation is checked for example to determine whether theuser 131 a paid the fare.

At 1005, the enforcement computer 175 sends a message to the mobiledevice 130 a with the validation check results. that the user isvalidated if the user is determined to be validated. Otherwise, at 1006,a message is sent indicating validation failure. Validation results mayalso be displayed on display.

FIG. 11 illustrates another method for enforcement. At 1101, aninspection signal is transmitted by at least one inspection beacon. Theinspection signal includes an enforcement variable for calculating anenforcement ID. The enforcement variable may be changed periodically.For example, the enforcement variable may be changed at predeterminedintervals and/or at different locations (e.g., at different stops if theinspection area is mobile, such as in a vehicle).

At 1102, the mobile devices 130 within range of the inspection signalreceive the inspection signal and enter inspection mode whereby farebuying via the validation and enforcement applications 132 is disabled.

At 1103, the mobile devices 130 that received the inspection signal andthat are in inspection mode each calculate an enforcement displayindicator based on the enforcement variable in the inspection signal anda determination of whether the user associated with the mobile devicehas been validated. For example, the validation and enforcementapplication on a mobile device determines whether the mobile devicestores an indication of whether the fare has been paid for the currentvalidation and enforcement area. A recent transaction summary stored onthe mobile device may be checked to determine whether the user iscurrently validated. The mobile device stores a function for calculatingthe enforcement display indicator from the enforcement variable in theinspection signal and a determination of whether the user associatedwith the mobile device has been validated. In a simple example, thefunction may be modulo(enforcement variable*validation determination),whereby the enforcement variable is an integer greater than or equal to1 and the validation determination is 0 or 1 depending on whether theuser is validated. If the validation determination is 0 (e.g., meaningthe user is not validated), the function returns “undefined” or anerror, and an indication of non-validation is displayed on a display ofthe mobile device at 1104. If the validation determination is 1 (e.g.,meaning that the user is validated), the enforcement display indicatoris displayed on the mobile device at 1105. Of course, other functionsmay be used. The output of the function may be the enforcement displayindicator or the enforcement display indicator may be derived from theoutput of the function.

The enforcement computer 175 stores the same function as the mobiledevice, e.g., modulo(enforcement variable*validation determination). Theenforcement computer 175 also stores the current enforcement variable.At 1106, the enforcement computer 175 also calculates the output of thefunction assuming the user is validated (e.g., the validationdetermination is 1) and displays the enforcement display indicator(which may be the output of the function or may be derived from theoutput of the function) on a display of the enforcement computer 175.Then, the enforcement individual can ask each user that is in apredetermined proximity to the enforcement computer 175 to show theirmobile device that is displaying the enforcement display indicator. Ifthe mobile device is displaying the same value as the display on theenforcement computer 175, the enforcement individual can quicklydetermine the user is validated; otherwise the user may not bevalidated. Instead of displaying a value, a specific picture may bedetermined according to the inputs of the enforcement variable and thevalidation determination is determined and displayed.

FIG. 12 illustrates a method 1200 to enable auto-payment via thevalidation and enforcement application 132 a and automatically deductthe fare for validation. The validation and enforcement area 101 forexample provides a fare-based service, such as a subway or train stationthat charges a fare to passengers that ride the train. Also, thevalidation and enforcement application 132 a includes modules to enablefare payment. FIG. 12 shows enabling auto-payment, however, thevalidation and enforcement application 132 a may also allow the user topay the fare on demand in response to user input. For example, if theuser enters the validation and enforcement area 101, the validation andenforcement application 132 a may detect that the mobile device 130 a isin the validation and enforcement application 132 a and displays ascreen that allows the user to select payment of the fare.

At 1201, the user 131 a logs into their account. The user 131 a may haveto create an account if they don't have one. The validation andenforcement application 132 a provides a graphical user interface on themobile device 130 a to receive a login ID and password and send theinformation to a backend server to login the user 131 a into theiraccount. At 1202, the validation and enforcement application 132 a addsfare products to the account based on user selections. Fare productsincludes any goods or services for which the user is authorizingpayment. At 1203, the validation and enforcement application 132 aenables auto-payment of the selected fare products in response to userinput. At 1204, the mobile device 130 a is detected in the validationand enforcement area 101, such as a zone or a fare-gate lane. The mobiledevice 130 a may remain in the user's pocket or bag to pay the fare,which is more convenient for the user. At 1205, the user's account isautomatically deducted. The amount deducted is based on the fare schemeused by the transit entity, which may be based on distance, day pass,etc. In one example, a single fare is charged regardless of distancetraveled. In another example, distance traveled or number of stops isdetermined to calculate the fare and the fare is deducted. To determinethe distance traveled or number of stops traveled (e.g., when the useris a passenger on the train) the validation and enforcement applicationon the mobile device determines when the user leaves the train or leavesa train station. For example, the mobile device of the user may receivea signal via the short-distance communication interface of the mobiledevice from a beacon at an exit to the train station or near the exit ofthe vehicle that indicates the user has left the train or train station.The signal may identify the train station, so the validation andenforcement application can determine the train station where the usergot on the train and the train station where the user got off the trainin order to calculate the fare.

What has been described and illustrated herein is an example along withsome of its variations. The terms, descriptions and figures used hereinare set forth by way of illustration only and are not meant aslimitations. Many variations are possible within the spirit and scope ofthe subject matter, which is intended to be defined by the followingclaims—and their equivalents—in which all terms are meant in theirbroadest reasonable sense unless otherwise indicated.

What is claimed is:
 1. A secure short-distance-based communication andenforcement system comprising: a plurality of beacons in a validationand enforcement area; a zone computer comprising: a short-distancecommunication interface to communicate with a mobile device if themobile device is in the validation and enforcement area; and a processorto determine whether the mobile device is in the validation andenforcement area and determine whether a unique mobile device identifier(ID) is received from the mobile device via the short-distancecommunication interface, wherein the unique mobile device ID isdetermined based on a broadcasted signal received from at least one ofthe plurality of beacons, in response to determining the mobile deviceis in the validation and enforcement area and in response to determiningthe unique mobile device ID is received, the processor exchangingvalidation messages with the mobile device using the unique mobiledevice ID to validate a user associated with the mobile device, andsending a signal via the short-distance communication interface to themobile device indicating whether the user is validated or not; and anenforcement computer comprising: at least one short-distancecommunication interface; and a processor to invoke an inspection beaconto broadcast an inspection signal via at least one short-distancecommunication interface, wherein in response to the mobile devicereceiving the inspection signal, the mobile device enters an inspectionmode and disables fare buying on the mobile device for a fare associatedwith the validation and enforcement area, and the processor of theenforcement computer exchanges inspection messages with the mobiledevice via the at least one short-distance communication interface todetermine whether the user is validated when the mobile device is ininspection mode.
 2. The secure short-distance-based communication andenforcement system of claim 1, wherein at least one of the plurality ofbeacons in the validation and enforcement area comprises the inspectionbeacon, and to invoke the inspection beacon to broadcast the inspectionsignal, the processor in the enforcement computer sends an inspectionmode signal to the plurality of beacons in the validation andenforcement area, and the plurality of beacons enter an inspectionbeacon mode and broadcast the inspection signal.
 3. The secureshort-distance-based communication and enforcement system of claim 1,wherein the enforcement computer comprises a mobile device including theinspection beacon.
 4. The secure short-distance-based communication andenforcement system of claim 1, wherein in response to the mobile devicereceiving the inspection signal, the mobile device calculates aninspection ID from information in the inspection signal, wherein theinspection ID is unique to the mobile device, and sends the inspectionID to the enforcement computer.
 5. The secure short-distance-basedcommunication and enforcement system of claim 4, wherein the enforcementcomputer is to receive the inspection ID via the at least oneshort-distance communication interface, and the processor of theenforcement computer is to determine whether the mobile device is in anarea of inspection of the enforcement computer, and in response todetermining the mobile device is in the area of inspection, engage inthe exchange of the inspection messages with the mobile device using theinspection ID to determine whether the user is validated.
 6. The secureshort-distance-based communication and enforcement system of claim 1,wherein the enforcement computer comprises a network interface tocommunicate with a backend server via at least one of a local areanetwork and a wide area network, and the processor sends a validationrequest to the backend server to determine whether the user paid thefare.
 7. The secure short-distance-based communication and enforcementsystem of claim 1, wherein the enforcement computer comprises a display,and the processor of the enforcement computer displays an indication ofwhether the user is validated on the display.
 8. The secureshort-distance-based communication and enforcement system of claim 1,wherein the processor of the enforcement computer sends a message to themobile device with an indication of whether the user is validated. 9.The secure short-distance-based communication and enforcement system ofclaim 8, wherein the mobile device is to exit the inspection mode andallow fare payment through the mobile device after receiving the messagewith the indication of whether the user is validated.
 10. The secureshort-distance-based communication and enforcement system of claim 1,wherein the user is validated if the fare is paid, and the enforcementcomputer is to store an indication that the user is validated inresponse to determining the fare was paid or is enabled to be paid. 11.A mobile device comprising: at least one short-distance communicationinterface to receive a signal including a beacon ID) from at least onebeacon in a validation and enforcement area; a data storage storing anoperating system and a validation and enforcement application; and aprocessor executing the operating system, wherein the operating systemdetermines whether the received beacon ID is a registered beacon ID, andin response to determining the beacon ID is a registered beacon ID,launching the validation and enforcement application stored on themobile device, wherein the validation and enforcement application, inresponse to being launched, is executed by the processor, and thevalidation and enforcement application determines whether the mobiledevice is in a validation and enforcement area, in response todetermining the mobile device is in the validation and enforcement area,calculating a unique mobile device ID for the mobile device based on thebeacon ID, wherein the unique mobile device ID is only valid for themobile device and a zone where the mobile device is currently located,wherein the validation and enforcement application engages in securecommunication with a zone computer or an enforcement computer for thevalidation and enforcement area using the unique mobile device ID and atleast one encryption key via the at least one short-distancecommunication interface to validate a user associated with the mobiledevice or to determine whether the user is validated.
 12. The mobiledevice of claim 11, wherein the processor determines whether the beaconID is for an inspection beacon, and in response to determining thebeacon ID is for the inspection beacon, disabling fare buying throughthe validation and enforcement application, and exchanging inspectionmessages with the enforcement computer using the inspection ID via theat least one short-distance communication interface to verify the useris validated.
 13. The mobile device of claim 12, wherein the inspectionmessages include a message received from the enforcement computer withan indication of whether the user is validated, and the processor is toexit the inspection mode and allow fare payment through the validationand enforcement application after receiving the message with theindication of whether the user is validated.
 14. The mobile device ofclaim 13, wherein the user is validated if a fare is paid, and theenforcement computer is to store an indication that the user isvalidated in response to determining the fare was paid or is enabled tobe paid.
 15. The mobile device of claim 13, wherein the mobile deviceincludes an input/output (I/O) device, and the validation andenforcement application generates an indication of whether the user isvalidated through the I/O device based on the message with theindication of whether the user is validated.
 16. A mobile devicevalidation and inspection method comprising: receiving a signal from abeacon via at least one short-distance communication interface of amobile device; determining whether the received beacon signal is from aregistered beacon; if the received beacon signal is from a registeredbeacon, determining whether the received beacon signal is an inspectionsignal from an inspection beacon; if the received beacon signal is aninspection signal, disabling fare purchasing from the mobile device, andexchanging inspection messages with an enforcement computer to determineif a user associated with the mobile device is validated; and enablingthe fare purchasing in response to determining whether the user isvalidated, wherein the fare purchasing is for purchasing a fare to be ina validation and enforcement area.
 17. The method of claim 16, whereinif the received beacon signal is not from a registered beacon, ignoringthe received beacon signal.
 18. The method of claim 16, comprising: ifthe received beacon signal is from a registered beacon, determiningwhether the received beacon signal is a validation signal or theinspection signal; and if the received beacon signal is the validationsignal, exchanging validation messages with a zone computer to validatethe user.
 19. A method performed by an enforcement computer in a secureshort-distance-based communication and enforcement system, the methodcomprising: receiving an inspection ID from a mobile device in avalidation and enforcement area; determining whether the mobile deviceis in an area of inspection of the enforcement computer; if the mobiledevice is not in the area of inspection, ignoring the inspection ID; ifthe mobile device is in the area of inspection, exchanging inspectionmessages with the mobile device using the inspection ID and determiningwhether a user associated with the mobile device is validated to be inthe validation and enforcement area based on the exchanged messages;sending a message to the mobile device indicating whether the user isvalidated and displaying, at the enforcement computer, an indication ofwhether the user is validated.
 20. The method of claim 20, wherein thevalidation and enforcement area is inside a vehicle, and determiningwhether the user is validated comprises determining whether the userpaid a fare to ride in the vehicle.
 21. A method for validationenforcement comprising: transmitting an inspection signal from at leastone beacon, wherein the inspection signal includes an enforcementvariable that is changed at predetermined intervals or at differentlocations; receiving the inspection signal at least one mobile devicewithin range of the at least one beacon; disabling fare purchasing fromthe at least one mobile device; determining, at the at least one mobiledevice, an enforcement display indicator at the at least one mobiledevice according to a predetermined function and based on theenforcement variable in the inspection signal and a determination ofwhether a user associated with the at least one mobile device has beenvalidated; displaying the enforcement display indicator on the at the atleast one mobile device; determining the enforcement display indicatorat the enforcement computer according to the same predetermined functionand based on the enforcement variable transmitted in the inspectionsignal and an assumption that the user has been validated; anddisplaying on a display of the enforcement computer, the enforcementdisplay indicator determined at the enforcement computer.